home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Tools (InfoMagic)
/
Internet Tools.iso
/
dos_win
/
winsock
/
hacklist
/
94-04.Z
/
94-04
/
000017_natale@acec.com_Wed Apr 20 22:20:42 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-04-30
|
3KB
Received: from uu3.psi.com by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
id AA08205; Thu, 21 Apr 1994 10:26:27 -0400
Received: from acec.com by uu3.psi.com (5.65b/4.0.071791-PSI/PSINet) via SMTP;
id AA21108 for rcq@ftp.com; Thu, 21 Apr 94 02:21:42 -0400
Date: Thu, 21 Apr 1994 02:20:42 -0400
From: natale@acec.com (Bob Natale)
Received: by nips.acec.com (5.65/3.2.083191-American Computer and Electronics Corp. )
id AA21937; Thu, 21 Apr 1994 02:20:42 -0400
Message-Id: <9404210620.AA21937@nips.acec.com>
To: rcq@ftp.com
Subject: Re: closesocket()/WSACleanup() question
Cc: winsock-hackers@sunsite.unc.edu
> Date: Fri, 15 Apr 1994 22:22:51 -0400
> From: rcq@ftp.com (Bob Quinn)
Hi BobQ,
> graceful close. So, a DLL cannot be faulted if it resets the
> connection when an application calls WSACleanup(), even if
> closesocket() was called before. The application wouldn't
> know the difference either way.
>
> My take on it is that if an application really cares about its
> data and/or having a graceful close of the connection, then it
> should wait until the socket is closed before calling WSACleanup().
> In other words, the onus should be on the application, not on the
> WinSock DLL and stack. This is easily accomplished in an applica-
> tion with FD_CLOSE notification, among other methods.
>
> Comments?
Your position seems eminently reasonable to me.
BobN
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Bob Natale American Computer 301-258-9850 [tel]
Director 209 Perry Pkwy 301-921-0434 [fax]
Network Mgmt Products Gaithersburg MD 20877 natale@acec.com
From pbh@MIT.EDU Thu Apr 21 11:02:47 1994
Received: from MIT.EDU (MIT.MIT.EDU) by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
id AA13851; Thu, 21 Apr 1994 11:02:47 -0400
Received: from ASHPOOL.MIT.EDU by MIT.EDU with SMTP
id AA01502; Thu, 21 Apr 94 11:02:45 EDT
Message-Id: <9404211502.AA01502@MIT.EDU>
To: Multiple recipients of list <winsock-hackers@sunsite.unc.edu>
Subject: WSAStartup() question
Date: Thu, 21 Apr 94 11:02:44
From: pbh@MIT.EDU
Suppose I have the following application structure:
---------------------
my.exe
---------------------
| |
| |
| |
^ ^
------------ ---------------
auth.dll gen.dll
------------ ---------------
| |
| |
| |
-----------------
winsock.dll
-----------------
Should I call WSAStartup() in my.exe and not in the other two DLLs or
should I call it in auth.dll and gen.dll? Can WSACleanup() be called in a
wep()? What are the advantages/disavantages?